Summary

extracted from #149137 (comment):

sometimes validationErrors and packagePolicy goes out of sync:

this happens when our extension component fires an effect on mount to initialize the package policy before fleet's effect (init())

making this property stateful makes the extension component render only after fleet's effect has fired, which sorts out the ordering.

still kinda odd they are not in sync tho, even if fleet's effect fires last, i'd expect the policy to be changed as well. you can check the logs and reproduce this on env by going to the install page -> canceling and going in again

@nchaulet

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

For maintainers

• This was checked for breaking API changes and was labeled appropriately